Error Response Format
All SuperDoc API errors follow a consistent JSON structure:string
required
Machine-readable error code for programmatic handling
string
required
HTTP status text (e.g., “Bad Request”, “Unauthorized”)
string
required
Human-readable error description
string
required
Unique identifier for the request (useful for support)
string
ISO 8601 timestamp when the error occurred
HTTP Status Codes
SuperDoc API uses standard HTTP status codes:400 Bad Request
400 Bad Request
Client Error - Invalid request format or parametersCommon causes:
- Missing required parameters
- Invalid file format
- Malformed request body
- File too large
403 Forbidden
403 Forbidden
Authorization Error - Valid credentials but insufficient permissions
Common causes: - Plan limitations exceeded - Feature not available in current
plan - IP address restrictions
429 Too Many Requests
429 Too Many Requests
Rate Limiting - Request quota exceeded Common causes: - Hourly rate limit
exceeded - Daily rate limit exceeded - Burst limit exceeded
500 Internal Server Error
500 Internal Server Error
Server Error - Unexpected server-side issue Common causes: - Temporary
service disruption - Document processing failure - Resource exhaustion
Common Error Codes
Authentication Errors
File Processing Errors
Rate Limiting Errors
Error Handling Strategies
Basic Error Handling
Advanced Error Handling with Retry Logic
Error Handling Best Practices
Use specific error handling
Use specific error handling
Handle different error types with appropriate responses:
Log errors for debugging
Log errors for debugging
Always log errors with context:
Provide user-friendly messages
Provide user-friendly messages
Translate technical errors into user-friendly messages:
Implement graceful degradation
Implement graceful degradation
Provide alternatives when the API is unavailable:
Monitoring and Alerting
Error Rate Monitoring
Track error rates to identify issues:Health Check Implementation
Getting Help
When encountering persistent errors:Check Status Page
Monitor service status and planned maintenance
Contact Support
Include the requestId for faster troubleshooting

